Interactive data object map

ABSTRACT

An interactive data object map system is disclosed in which large amounts of geographical, geospatial, and other types of data, geodata, objects, features, and/or metadata are efficiently presented to a user on a map interface. The interactive data object map system allows for rapid and deep analysis of various objects, features, and/or metadata by the user. A layer ontology may be displayed to the user. In various embodiments, when the user rolls a selection cursor over an object/feature an outline of the object/feature is displayed. Selection of an object/feature may cause display of metadata associated with that object/feature. The interactive data object map system may automatically generate feature/object lists and/or histograms based on selections made by the user. The user may perform geosearches, generate heatmaps, and/or perform keyword searches, among other actions.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.17/027,498, filed Sep. 21, 2020 and titled “INTERACTIVE DATA OBJECTMAP”, which is a continuation of U.S. patent application Ser. No.16/516,041, filed on Jul. 18, 2019, and titled “INTERACTIVE DATA OBJECTMAP”, which is a continuation of U.S. patent application Ser. No.14/323,878, filed on Jul. 3, 2014, and titled “INTERACTIVE DATA OBJECTMAP”, which is a continuation of U.S. patent application Ser. No.13/917,571, filed on Jun. 13, 2013, and titled “INTERACTIVE GEOSPATIALMAP,” which application claims a priority benefit under 35 U.S.C. § 119to U.S. Provisional Patent Application No. 61/820,608, filed on May 7,2013, and titled “INTERACTIVE DATA OBJECT MAP.” All of theabove-identified applications are hereby incorporated by referenceherein in their entireties.

TECHNICAL FIELD

The present disclosure relates to systems and techniques forgeographical data integration, analysis, and visualization. Morespecifically, the present disclosure relates to interactive mapsincluding data objects.

BACKGROUND

Interactive geographical maps, such as web-based mapping serviceapplications and Geographical Information Systems (GIS), are availablefrom a number of providers. Such maps generally comprise satelliteimages or generic base layers overlaid by roads. Users of such systemsmay generally search for and view locations of a small number oflandmarks, and determine directions from one location to another. Insome interactive graphical maps, 3D terrain and/or 3D buildings may bevisible in the interface.

SUMMARY

The systems, methods, and devices described herein each have severalaspects, no single one of which is solely responsible for its desirableattributes. Without limiting the scope of this disclosure, severalnon-limiting features will now be discussed briefly.

The systems, methods, and devices of the present disclosure may provide,among other features, high-performance, interactive geospatial and/ordata object map capabilities in which large amounts of geographical,geospatial, and other types of data, geodata, objects, features, and/ormetadata are efficiently presented to a user on a map interface. Invarious embodiments, an interactive geospatial map system (also referredto as an interactive data object map system) may enable rapid and deepanalysis of various objects, features, and/or metadata by the user. Insome embodiments, a layer ontology may be displayed to the user. Invarious embodiments, when the user rolls a selection cursor over anobject/feature an outline of the object/feature is displayed. Selectionof an object/feature may cause display of metadata associated with thatobject/feature. In various embodiments, the interactive data object mapsystem may automatically generate feature/object lists and/or histogramsbased on selections made by the user. Various aspects of the presentdisclosure may enable the user to perform geosearches, generateheatmaps, and/or perform keyword searches, among other actions.

In an embodiment, a computer system is disclosed comprising anelectronic data structure configured to store a plurality of features orobjects, wherein each of the features or objects is associated withmetadata; a computer readable medium storing software modules includingcomputer executable instructions; one or more hardware processors incommunication with the electronic data structure and the computerreadable medium, and configured to execute a user interface module ofthe software modules in order to: display an interactive map on anelectronic display of the computer system; include on the interactivemap one or more features or objects, wherein the features or objects areselectable by a user of the computer system, and wherein the features orobjects are accessed from the electronic data structure; receive a firstinput from the user selecting one or more of the included features orobjects; and in response to the first input, access, from the electronicdata structure, the metadata associated with each of the selectedfeatures or objects; determine one or more metadata categories based onthe accessed metadata; organize the selected features or objects intoone or more histograms based on the determined metadata categories andthe accessed metadata; and display the one or more histograms on theelectronic display.

According to an aspect, the features or objects may comprise vectordata.

According to another aspect, the features or objects may comprise atleast one of roads, terrain, lakes, rivers, vegetation, utilities,street lights, railroads, hotels or motels, schools, hospitals,buildings or structures, regions, transportation objects, entities,events, or documents.

According to yet another aspect, the metadata associated with thefeatures or objects may comprise at least one of a location, a city, acounty, a state, a country, an address, a district, a grade level, aphone number, a speed, a width, or other related attributes.

According to another aspect, the features or objects may be selectableby a user using a mouse and/or a touch interface.

According to yet another aspect, each histogram of the one or morehistograms may be specific to a particular metadata category.

According to another aspect, each histogram of the one or morehistograms may comprise a list of items of metadata specific to theparticular metadata category of the histogram, wherein the list of itemsis organized in descending order from an item having the largest numberof related objects or features to an item having the smallest number ofrelated objects or features.

According to yet another aspect, the one or more histograms displayed onthe electronic display may be displayed so as to partially overlay thedisplayed interactive map.

According to another aspect, the one or more hardware processors may befurther configured to execute the user interface module in order to:receive a second input from the user selecting a second one or morefeatures or objects from the one or more histograms; and in response tothe second input, update the interactive map to display the second oneor more features or objects on the display; and highlight the second oneor more features or objects on the interactive map.

According to yet another aspect, updating the interactive map maycomprise panning and/or zooming.

According to another aspect, highlighting the second one or morefeatures may comprise at least one of outlining, changing color,bolding, or changing contrast.

According to yet another aspect, the one or more hardware processors maybe further configured to execute the user interface module in order to:receive a third input from the user selecting a drill-down group offeatures or objects from the one or more histograms; and in response tothe third input, drill-down on the selected drill-down group of featuresor objects by: accessing the metadata associated with each of thefeatures or objects of the selected drill-down group; determining one ormore drill-down metadata categories based on the accessed metadataassociated with each of the features or objects of the selecteddrill-down group; organizing the features or objects of the selecteddrill-down group into one or more drill-down histograms based on thedetermined drill-down metadata categories and the accessed metadataassociated with each of the features or objects of the selecteddrill-down group; and displaying on the interactive map the one or moredrill-down histograms.

According to another aspect, the one or more hardware processors may befurther configured to execute the user interface module in order toenable the user to further drill down into the one or more drill-downhistograms.

According to yet another aspect, the one or more hardware processors maybe further configured to execute the user interface module in order to:receive a feature or object hover over input from the user; and inresponse to receiving the hover over input, highlight, on the electronicdisplay, metadata associated with the particular hovered over feature orobject to the user.

According to another aspect, one or more hardware processors may befurther configured to execute the user interface module in order to:receive a feature or object selection input from the user; and inresponse to receiving the selection input, display, on the electronicdisplay, metadata associated with the particular selected feature orobject to the user.

In another embodiment, a computer system is disclosed comprising: anelectronic data structure configured to store a plurality of features orobjects, wherein each of the features or objects is associated withmetadata; a computer readable medium storing software modules includingcomputer executable instructions; one or more hardware processors incommunication with the electronic data structure and the computerreadable medium, and configured to execute a user interface module ofthe software modules in order to: display an interactive map on adisplay of the computer system, the interactive map comprising aplurality of map tiles accessed from the electronic data structure, themap tiles each comprising an image composed of one or more vectorlayers; include on the interactive map a plurality of features orobjects accessed from the electronic data structure, the features orobjects being selectable by a user, each of the features or objectsincluding associated metadata; receive an input from a user including atleast one of a zoom action, a pan action, a feature or object selection,a layer selection, a geosearch, a heatmap, and a keyword search; and inresponse to the input from the user: request, from a server, updated maptiles, the updated map tiles being updated according to the input fromthe user; receive the updated map tiles from the server; and update theinteractive map with the updated map tiles.

According to an aspect, the one or more vector layers may comprise atleast one of a regions layer, a buildings/structures layer, a terrainlayer, a transportation layer, or a utilities/infrastructure layer.

According to an aspect, each of the one or more vector layers may becomprised of one or more sub-vector layers.

In yet another embodiment, a computer system is disclosed comprising:one or more hardware processors in communication with the computerreadable medium, and configured to execute a user interface module ofthe software modules in order to: display an interactive map on adisplay of the computer system, the interactive map comprising aplurality of map layers; determine a list of available map layers;organizing the list of available map layers according to a hierarchicallayer ontology, wherein like map layers are grouped together; anddisplay on the interactive map the hierarchical layer ontology, whereinthe user may select one or more of the displayed layers, and whereineach of the available map layers is associated with one or more featureor object types.

According to an aspect, the map layers may comprise at least one ofvector layers and base layers.

BRIEF DESCRIPTION OF THE DRAWINGS

The following aspects of the disclosure will become more readilyappreciated as the same become better understood by reference to thefollowing detailed description, when taken in conjunction with theaccompanying drawings.

FIG. 1 illustrates a sample user interface of the interactive dataobject map system, according to an embodiment of the present disclosure.

FIG. 2A illustrates a sample user interface of the interactive dataobject map system in which map layers are displayed to a user, accordingto an embodiment of the present disclosure.

FIG. 2B illustrates an example map layer ontology, according to anembodiment of the present disclosure.

FIG. 2C illustrates a sample user interface of the interactive dataobject map system in which various objects are displayed, according toan embodiment of the present disclosure.

FIG. 3A illustrates a sample user interface of the interactive dataobject map system in which objects are selected, according to anembodiment of the present disclosure.

FIGS. 3B-3G illustrate sample user interfaces of the interactive dataobject map system in which objects are selected and a histogram isdisplayed, according to embodiments of the present disclosure.

FIGS. 3H-3I illustrate sample user interfaces of the interactive dataobject map system in which objects are selected and a list of objects isdisplayed, according to embodiments of the present disclosure.

FIGS. 3J-3K illustrate sample user interfaces of the interactive dataobject map system in which objects are outlined when hovered over,according to embodiments of the present disclosure.

FIGS. 4A-4D illustrate sample user interfaces of the interactive dataobject map system in which a radius geosearch is displayed, according toembodiments of the present disclosure.

FIGS. 5A-5D illustrate sample user interfaces of the interactive dataobject map system in which a heatmap is displayed, according toembodiments of the present disclosure.

FIGS. 5E-5F illustrate sample user interfaces of the interactive dataobject map system in which a shape-based geosearch is displayed,according to embodiments of the present disclosure.

FIG. 5G illustrates a sample user interface of the interactive dataobject map system in which a keyword object search is displayed,according to an embodiment of the present disclosure.

FIG. 5H illustrates an example of a UTF grid of the interactive dataobject map system, according to an embodiment of the present disclosure.

FIG. 6A shows a flow diagram depicting illustrative client-sideoperations of the interactive data object map system, according to anembodiment of the present disclosure.

FIG. 6B shows a flow diagram depicting illustrative client-side metadataretrieval of the interactive data object map system, according to anembodiment of the present disclosure.

FIG. 7A shows a flow diagram depicting illustrative server-sideoperations of the interactive data object map system, according to anembodiment of the present disclosure.

FIG. 7B shows a flow diagram depicting illustrative server-side layercomposition of the interactive data object map system, according to anembodiment of the present disclosure.

FIG. 8A illustrates one embodiment of a database system using anontology.

FIG. 8B illustrates one embodiment of a system for creating data in adata store using a dynamic ontology.

FIG. 8C illustrates a sample user interface using relationshipsdescribed in a data store using a dynamic ontology.

FIG. 8D illustrates a computer system with which certain methodsdiscussed herein may be implemented.

DETAILED DESCRIPTION OF SPECIFIC EMBODIMENTS Overview

In general, a high-performance, interactive data object map system (or“map system”) is disclosed in which large amounts of geographical,geospatial, and other types of data, geodata, objects, features, and/ormetadata are efficiently presented to a user on a map interface. Theinteractive data object map system allows for rapid and deep analysis ofvarious objects, features, and/or metadata by the user. For example,millions of data objects and/or features may be simultaneously viewedand selected by the user on the map interface. A layer ontology may bedisplayed to the user that allows the user to select and view particularlayers. In various embodiments, when the user rolls a selection cursorover an object/feature (and/or otherwise selects the object/feature) anoutline of the object/feature is displayed. Selection of anobject/feature may cause display of metadata associated with thatobject/feature.

In an embodiment, the user may rapidly zoom in and out and/or move andpan around the map interface to variously see more or less detail, andmore or fewer objects. In various embodiments, the interactive dataobject map system may automatically generate feature/object lists and/orhistograms based on selections made by the user. In various embodiments,the user may perform geosearches (based on any selections and/or drawnshapes), generate heatmaps, and/or perform keyword searches, among otheractions as described below.

In an embodiment, the interactive data object map system includesserver-side computer components and/or client-side computer components.The client-side components may implement, for example, displaying maptiles, showing object outlines, allowing the user to draw shapes, and/orallowing the user to select objects/features, among other actions. Theserver-side components may implement, for example, composition of layersinto map tiles, caching of composed map tiles and/or layers, and/orproviding object/feature metadata, among other actions. Such functionsmay be distribution in any other manner. In an embodiment,object/feature outlines and/or highlighting are accomplished on theclient-side through the use of a UTF grid.

Definitions

In order to facilitate an understanding of the systems and methodsdiscussed herein, a number of terms are defined below. The terms definedbelow, as well as other terms used herein, should be construed toinclude the provided definitions, the ordinary and customary meaning ofthe terms, and/or any other implied meaning for the respective terms.Thus, the definitions below do not limit the meaning of these terms, butonly provide exemplary definitions.

Ontology: A hierarchical arrangement and/or grouping of data accordingto similarities and differences. The present disclosure describes twoontologies. The first relates to the arrangement of vector layersconsisting of map and object data as used by the interactive data objectmap system (as described below with reference to FIGS. 2A-2B). Thesecond relates to the storage and arrangement of data objects in one ormore databases (as described below with reference to FIGS. 8A-8C). Forexample, the stored data may comprise definitions for object types andproperty types for data in a database, and how objects and propertiesmay be related.

Database: A broad term for any data structure for storing and/ororganizing data, including, but not limited to, relational databases(Oracle database, mySQL database, etc.), spreadsheets, XML files, andtext file, among others.

Data Object, Object, or Feature: A data container for informationrepresenting specific things in the world that have a number ofdefinable properties. For example, a data object can represent an entitysuch as a person, a place, an organization, a market instrument, orother noun. A data object can represent an event that happens at a pointin time or for a duration. A data object can represent a document orother unstructured data source such as an e-mail message, a news report,or a written paper or article. Each data object may be associated with aunique identifier that uniquely identifies the data object. The object'sattributes (e.g. metadata about the object) may be represented in one ormore properties. For the purposes of the present disclosure, the terms“feature,” “data object,” and “object” may be used interchangeably torefer to items displayed on the map interface of the interactive dataobject map system, and/or otherwise accessible to the user through theinteractive data object map system. Features/objects may generallyinclude, but are not limited to, roads, terrain (such as hills,mountains, rivers, and vegetation, among others), street lights (whichmay be represented by a streetlight icon), railroads, hotels/motels(which may be represented by a bed icon), schools (which may berepresented by a parent-child icon), hospitals, other types of buildingsor structures, regions, transportation objects, and other types ofentities, events, and documents, among others. Objects displayed on themap interface generally comprise vector data, although other types ofdata may also be displayed. Objects generally have associated metadataand/or properties.

Object Type: Type of a data object (e.g., Person, Event, or Document).Object types may be defined by an ontology and may be modified orupdated to include additional object types. An object definition (e.g.,in an ontology) may include how the object is related to other objects,such as being a sub-object type of another object type (e.g. an agentmay be a sub-object type of a person object type), and the propertiesthe object type may have.

Properties: Also referred to as “metadata,” includes attributes of adata object/feature. At a minimum, each property/metadata of a dataobject has a type (such as a property type) and a value or values.Properties/metadata associated with features/objects may include anyinformation relevant to that feature/object. For example, metadataassociated with a school object may include an address (for example, 123S. Orange Street), a district (for example, 509c), a grade level (forexample, K-6), and/or a phone number (for example, 800-0000), amongother items of metadata. In another example, metadata associated with aroad object may include a speed (for example, 25 mph), a width (forexample, 2 lanes), and/or a county (for example, Arlington), among otheritems of metadata.

Property Type: The data type of a property, such as a string, aninteger, or a double. Property types may include complex property types,such as a series data values associated with timed ticks (e.g. a timeseries), etc.

Property Value: The value associated with a property, which is of thetype indicated in the property type associated with the property. Aproperty may have multiple values.

Link: A connection between two data objects, based on, for example, arelationship, an event, and/or matching properties. Links may bedirectional, such as one representing a payment from person A to B, orbidirectional.

Link Set: Set of multiple links that are shared between two or more dataobjects.

DESCRIPTION OF THE FIGURES

Embodiments of the disclosure will now be described with reference tothe accompanying Figures, wherein like numerals refer to like elementsthroughout. The terminology used in the description presented herein isnot intended to be interpreted in any limited or restrictive manner,simply because it is being utilized in conjunction with a detaileddescription of certain specific embodiments of the disclosure.Furthermore, embodiments of the disclosure may include several novelfeatures, no single one of which is solely responsible for its desirableattributes or which is essential to practicing the embodiments of thedisclosure herein described.

FIG. 1 illustrates a sample user interface of the interactive dataobject map system, according to an embodiment of the present disclosure.The user interface includes a map interface 100, a selection button/icon102, a shape button/icon 104, a layers button/icon 106, a geosearchbutton/icon 108, a heat map button/icon 110, a search box 112, a featureinformation box 114, a coordinates information box 116, map scaleinformation 118, zoom selectors 120, and highlighted features 122. Thefunctionality of the interactive data object map system may beimplemented in one or more computer modules and/or processors, as isdescribed below with reference to FIG. 8D.

The map interface 100 of FIG. 1 is composed of multiple map tiles. Themap tiles are generally composed of multiple layers of geographical,vector, and/or other types of data. Vector data layers (also referred toas vector layers) may include associated and/or linked dataobjects/features. In an embodiment, vector layers are composed of dataobjects/features. The various data objects and/or features associatedwith a particular vector layer may be displayed to the user when thatparticular vector layer is activated. For example, a transportationvector layer may include road, railroad, and bike path objects and/orfeatures that may be displayed to the user when the transportation layeris selected. The layers used to compose the map tiles and the mapinterface 100 may vary based on, for example, whether a user hasselected features displayed in the map interface 100, and/or theparticular layers a user has selected for display. In an embodiment,composition of map tiles is accomplished by server-side components ofthe interactive data object map system. In an embodiment, composed maptiles may be cached by the server-side components to speed up map tiledelivery to client-side components. The map tiles may then betransmitted to the client-side components of the interactive data objectmap system where they are composed into the map interface 100.

In general, the user interface of FIG. 1 is displayed on an electronicdisplay viewable by a user of the interactive data object map system.The user of the interactive data object map system may interact with theuser interface of FIG. 1 by, for example, touching the display when thedisplay is touch-enabled and/or using a mouse pointer to click on thevarious elements of the user interface.

The map interface 100 includes various highlighted features 122 andfeature icons. For example, the map interface 100 includes roads,buildings and structures, utilities, lakes, rivers, vegetation, andrailroads, among other features. The user may interact with the mapinterface 100 by, for example, rolling over and/or clicking on variousfeatures. In one embodiment, rolling over and/or placing the mousepointer over a feature causes the feature to be outlined and/orotherwise highlighted. Additionally, the name of the feature and/orother information about the feature may be shown in the featureinformation box 114.

The user of the map system may interact with the user interface of FIG.1 by scrolling or panning up, down, and/or side to side; zooming in orout; selecting features; drawing shapes; selecting layers; performing ageosearch; generating a heat map; and/or performing a keyword search;among other actions as are described below. Various user actions mayreveal more or less map detail, and/or more or fewer features/objects.

FIG. 2A illustrates a sample user interface of the map system in whichmap layers are displayed to a user, according to an embodiment of thepresent disclosure. In the user interface of FIG. 2A, the user hasselected the layers button 106, revealing the layers window 202. Thelayers window 202 includes a list of base layers, vector layers, anduser layers. The base layers include, for example, overhead imagery,topographic, blank (Mercator), base map, aviation, and blank(unprojected). The vector layers include general categories such as, forexample, regions, buildings/structures, terrain, transportation, andutilities/infrastructure. While no user layers are included in the userinterface of FIG. 2A, user layers may be added by the user of the mapsystem, as is described below.

In an embodiment, the user may select one or more of the base layerswhich may be used during composition of the map tiles. For example,selection of the overhead imagery base layer will produce map tiles inwhich the underlying map tile imagery is made up of recent aerialimagery. Similarly, selection of the topographic base layer will producemap tiles in which the underlying map tile imagery includes topographicmap imagery.

Further, in an embodiment, the user may select one or more of the vectorlayers which may be used during composition of the map tiles. Forexample, selecting the transportation layer results intransportation-related objects and/or features being displayed on themap tiles. Transportation-related features may include, for example,roads, railroads, street signs, and/or street lights, among others.Examples of transportation-related features may be seen in the userinterface of FIG. 2A where various roads, railroads, and street lighticons are displayed.

In an embodiment, the user of the map system may create and save maplayers. These saved map layers may be listed as user layers in thelayers window 202.

FIG. 2B illustrates an example map layer ontology, according to anembodiment of the present disclosure. As mentioned above with referenceto FIG. 2A, the list of vector layers in the layers window 202 mayinclude general categories/layers such as regions, buildings/structures,terrain, transportation, and utilities/infrastructure. The vector layersavailable in the map system may be further organized into an ontology,or hierarchical arrangement. For example, as shown in the vector layerswindow 206, the buildings/structures category 208 may be furthersubdivided into layers including structures, government, medical,education, and commercial. The terrain category 210 may includevegetation and/or water/hydrography layers. The utilities/infrastructurecategory may include fire and/or storage/draining.

In an embodiment, the user of the map system may select one or more ofthe layers and/or sub-layers of the layer ontology. As shown in FIG. 2B,the user has deselected the vegetation sub-layer, and all of theutilities/infrastructure layers. Selecting and deselecting vectorlayers, or toggling vectors layers on and off, may cause the vectorobjects and/or features associated with those layers to be displayed ornot displayed in the map interface. For example, when the user selectsthe transportation category/layer, road objects associated with thetransportation layer may be displayed on the map interface. Likewise,when a user deselects the transportation category/layer, road objectsassociated with the transportation layer may be removed from the mapinterface.

In an embodiment, additional hierarchical levels of layers may bedisplayed to the user. For example, the vector layers window 206 mayinclude sub-sub-layers (for example, the education sub-layer may bedivided into elementary schools, secondary schools, and post-secondaryschools). Alternatively, fewer hierarchical levels may be displayed tothe user.

In an embodiment, each of the vector layers shown in the vector layerswindow 206 may be made up of many layers of map vector data. In thisembodiment, the map system may advantageously generate a simplifiedlayer ontology, such as the one shown in 206. The simplified layerontology allows the user to easily select layers of interest from areduced number of layers, rather than a large number of discrete layers.As described above, vector layers may contain data regarding associatedfeatures and/or objects. Thus, features visible in the map interfacecorrespond to the currently active/selected layers. In an embodiment,the layer ontology may have an arbitrary depth.

FIG. 2C illustrates a sample user interface of the map system in whichvarious objects are displayed, according to an embodiment of the presentdisclosure. The user interface of FIG. 2C includes a map interface 214,an outlined feature 216, and feature information box 114 indicating thatthe outlined feature 216 is called “Union Park.” Variousfeatures/objects may be seen in the map interface 214 including, forexample, roads, buildings, terrain, street lights (represented by astreetlight icon), railroads, hotels/motels (represented by a bed icon),and schools (represented by a parent-child icon), among other features.

FIG. 3A illustrates a sample user interface of the map system in whichobjects are selected, according to an embodiment of the presentdisclosure. The user interface of FIG. 3A includes a highlighted userselection rectangle 302. The highlighted user selection rectangle 302illustrates the user actively selecting a particular region of the mapinterface so as to select the features/objects that fall within thebounds of that rectangle. In an embodiment, visible features may beselected by the user, while features that are not currently visible arenot selectable. For example, features related to layers that are notcurrently active are not selected when the user performs a selection. Inanother embodiment, even features that are not visible in a selectedarea may be selected.

FIGS. 3B-3C illustrate sample user interfaces of the map system in whichobjects are selected and a feature histogram 304 is displayed in aselection window, according to embodiments of the present disclosure.The selected objects/features of FIG. 3B (including roads 310 and otherfeatures 312) may have been selected via the highlighted user selectionrectangle 302 of FIG. 3A. Selected features are indicated byhighlighting and/or altered colors on the map tiles making up the mapinterface.

Feature histogram 304 is shown in a selection window included in theuser interface of FIG. 3B. The histogram 304 shows a categorizedhistogram of all objects/features selected by the user in the mapinterface. The histogram divides the features into common buckets and/orcategories based on related metadata (also referred to as metadatacategories). For example, at 306, “Belongs to Layer” indicates that thefollowing histogram includes all selected features organized by layercategory. In this example there are over 70,000 selectedbuildings/structures features, over 40,000 selected facility features,and over 6,000 selected road features, among others. Further, thefeature histogram 304 includes histograms of the selected objectsorganized by account and acreage. In various embodiments, the map systemmay select histogram categories and/or metadata categories based on, forexample, the features selected and/or types of features selected, amongothers. Any other categorization of selected features may be displayedin the histograms of the feature histogram 304.

In an embodiment, the user of the map system may select a subset of theselected features for further analysis and/or histogram generation. Forexample, the user may select a subset comprising selected objectsbelonging to the road category by, for example, clicking on the roadsitem 308. This selection may result in “drilling down” to histograms ofthat subset of features, as shown in FIG. 3C. Thus, a drill-down groupof features/objects (for example, the subset of features/objects) may beused by the map system to determine new drill-down metadata categories,or buckets of related metadata. At 314 in FIG. 3C, the arrow iconindicates that of the originally selected 124,172 features, the featurehistogram now shows an analysis of the 6,724 features belonging to theroad category (see item 316). The feature histogram window of FIG. 3Cthus shows a new set of histograms organized by layer, address,addressed, and agency, among others. The user may thus “drill down” and“drill up” through the selected features via the displayed histograms.

In an embodiment, items selected in the feature histogram arecorrespondingly highlighted in the map interface of the map system. Forexample, in the map interface of FIG. 3B, the user has selected theroads in the histogram at 308. Corresponding features (in this example,roads) are thus highlighted in the map interface (as shown at 310).

FIGS. 3D-3G illustrate additional example user interfaces of the mapsystem in which objects are selected from a histogram andcorrespondingly highlighted in the map interface, according toembodiments of the present disclosure. In FIGS. 3D-3F, in the selectionwindow, the user is viewing a histogram of all selected roads organizedin a histogram according to the road speed limit. In FIG. 3D, the userhas selected (at 318) roads with speed limits of 55 and 65. Thecorresponding road features are highlighted in the map interface at, forexample 320. In FIG. 3E, the user has selected (at 322) roads with speedlimits of 35, 45, 40, 55, and 65. The corresponding road features arehighlighted in the map interface at, for example 324. In FIG. 3F, theuser has selected (at 326) roads with speed limits of 25. Thecorresponding road features are highlighted in the map interface at, forexample 328. In FIG. 3G, the user may “drill down” into the histogramby, for example, right clicking on an item and selecting “Remove otherobjects in histogram” (330).

FIGS. 3H and 3I illustrate sample user interfaces of the map system inwhich objects are selected and a list of selected objects 332 isdisplayed in the selection window, according to embodiments of thepresent disclosure. With reference to FIG. 3H, the list of features 332indicates that the user has drilled down further into the selectedfeatures of FIG. 3G by selecting a subset of selected featuresconsisting of only roads with speed limits of 20. Thus, the subset ofthe example of FIG. 3H includes the 163 features that are roads withspeed limits of 20. The user has additionally selected to view the listof features 332 in the selection window (rather than the featurehistogram). The list of features 332 lists each individual feature thatis included in the currently selected subset. For example, the listincludes S Central Av 334, among others.

In FIG. 3I, the user has selected feature Hamilton St at 336. In anembodiment, when a feature is selected from the list of features, themap interface automatically zooms to the location of that feature. Theuser may select the feature from the list of features by clicking on thename of the feature and/or the displayed thumbnail. In an embodiment,the map interface only zooms to the feature when the user clicks on,and/or selects, the thumbnail associated with the feature. In theexample of FIG. 3I, the map interface is automatically zoomed to thelocation of the selected Hamilton St, and the selected feature ishighlighted (338). Additionally, the name of the selected feature isshown in the feature information box 114. In an embodiment, the name ofthe selected feature is shown in the feature information box 114 whenthe user hovers the cursor over the thumbnail associated with thefeature in the list of features. In an embodiment, the selected featuremay be any other type of object, and may be outlined or otherwisehighlighted when selected.

In various embodiments, the user of the map system may select either thelist of features, or the feature histogram, of the selection window toview information about the selected features.

FIGS. 3J-3K illustrate sample user interfaces of the map system in whichobjects are outlined when hovered over, according to embodiments of thepresent disclosure. In FIG. 3J, the user is hovering over a buildingfeature with the mouse cursor. The feature being hovered over isautomatically outlined (340). Additionally, the name of the feature isdisplayed in the feature information box 114. In FIG. 3K, the user ishovering over a shelter feature with the mouse cursor. The feature beinghovered over is automatically outlined (342), and the name of thefeature is displayed in the feature information box 114. The user of themap system may, at any time, highlight and/or outline any feature/objectby rolling over, hovering over, selecting, and/or touching thatfeature/object in the map interface.

In various embodiments, the user may select a feature in order to view afeature information window. The feature information window may include,for example, metadata associated with the selected feature. For example,the user may select a building feature, resulting in a display ofinformation associated with that building feature such as the buildingsize, the building name, and/or the building address or location, amongothers. Metadata associated with features/objects may include anyinformation relevant to that feature/object. For example, metadataassociated with a school may include an address (for example, 123 S.Orange Street), a district (for example, 509c), a grade level (forexample, K-6), and/or a phone number (for example, 800-0000), amongother items of metadata. In an embodiment, a history of the object,changes made to the object, and/or user notes related to the object,among other items, may be displayed. In an embodiment, a user may editmetadata associated with a selected feature.

FIGS. 4A-4D illustrate sample user interfaces of the map system in whicha radius geosearch is displayed, according to embodiments of the presentdisclosure. In FIG. 4A, the user has selected the shape button 104 andis drawing a circle selection 404 on the map interface by firstselecting a center and then a radius. Shape window 402 indicates thecoordinates of the center of the circle selection, as well as the radiusof the circle selection. In various embodiments, any type of polygon orother shape may be drawn on the map interface to select features.

In FIG. 4B, the user has selected the geosearch button 108 so as toperform a geosearch within the selection circle 408. In an embodiment, ageosearch comprises a search through one or more databases of dataobjects, and metadata associated with those data objects, for anyobjects that meet the criteria of the geosearch. For example, ageosearch may search for any objects with geographic metadata and/orproperties that indicate the object may be geographically within, forexample, selection circle 408. A geosearch within a selected circle maybe referred to as a radius search. Geosearch window 406 indicatesvarious items of information related to the radius search, and includesvarious parameters that may be adjusted by the user. For example, thegeosearch window 406 includes a search area slider that the user mayslide to increase or decrease the radius of the selection circle 408.The user may also indicate a time range for the geosearch. In anembodiment, objects/features shown and/or searchable in the map systemmay include a time component and/or time metadata. Thus, for example,the user of the map system may specify a date or time period, resultingin the display of any objects/features with associated time metadata,for example, falling within the specified time period. In variousembodiments, associated time metadata may indicate, for example, a timethe feature was created, a time the feature was added to a database offeatures, a time the feature was previously added to a vector layer, atime the feature was last accessed by the map system and/or a user, atime the feature was built, and/or any combination of the foregoing.Alternatively, the user may select and/or search for objects/featureswithin particular time periods, as shown in FIG. 4B. The geosearchwindow 406 also allows the user to specify the types of objects to besearched, for example, entities, events, and/or documents, among others.

In an embodiment, the user of the map system may perform a search byclicking and/or touching a search button. The map system may thenperform a search of an object database for any objects matching thecriteria specified in the geosearch. For example, in the example of FIG.4B the map system will search for any objects with associated locationinformation that falls within the selection circle 408. Objects searchedby the map system may include objects other than those shown on the mapinterface. For example, in an embodiment the map system may access oneor more databases of objects (and object metadata) that may be unrelatedto the features currently shown in the map interface, or featuresrelated to the currently selected vector layers. The databases accessedmay include databases external to any database storing data associatedwith the map system. Any objects found in the geosearch may then be madeavailable to the user (as shown in FIG. 4B), and the user may be giventhe option of adding the objects to a new layer in the map interface (asshown in the geosearch information window 406).

FIG. 4C shows objects added to the map interface following the geosearchin FIG. 4B. The search results are also shown in the feature histogram410. In this example the returned objects include various entities andevents. FIG. 4D shows the user has selected, in the feature histogram,all search result objects with related metadata indicating a drug lawviolation. Those selected objects are additionally highlighted in themap interface of FIG. 4D. In another example, geosearch may be used todetermine, for example, that many crimes are concentrated in a downtownarea of a city, while DUIs are more common in areas with slow roads.

FIGS. 5A-5D illustrate sample user interfaces of the map system in whicha heatmap is displayed, according to embodiments of the presentdisclosure. In FIG. 5A, the user has selected the heatmap button 110 soas to create a heatmap 504 based on the objects selected in FIG. 4D. Aheatmap information window 502 is displayed in which the user mayspecify various parameters related to the generation of heatmap. Forexample, referring now to FIG. 5B, the user may adjust a radius (506) ofthe circular heatmap related to each selected object, an opacity (508)of the heatmap, a scale of the heatmap, and an auto scale setting. InFIG. 5B, the user has decreased the opacity of the generated heatmap andzoomed in on the map interface so as to more clearly view variousobjects and the underlying map tiles.

FIG. 5C shows the user selecting various objects and/or features whilethe heatmap is displayed using the rectangle selection tool, such as toview information regarding the features in a histogram. FIG. 5D showsthe selected objects, selected in FIG. 5C, now highlighted (512).

In the map system a heatmap may be generated on any object type, and/oron multiple object types. In an embodiment, different heatmap radiusesmay be set for different object types. For example, the user maygenerate a heatmap in which streetlights have a 20 m radius, whilehospitals have a 500 m radius. In an embodiment, the heatmap may begenerated based on arbitrary shapes. For example, rather than acircular-based heatmap, the heatmap may be rectangular-based orellipse-based. In an embodiment, the heatmap may be generated based onerror ellipses and/or tolerance ellipses. A heatmap based on errorellipses may be advantageous when the relevant objects have associatederror regions. For example, when a location of an object is uncertain,or multiple datapoints associated with an object are available, an errorellipse may help the user determine the actual location of the object.

FIGS. 5E-5F illustrate sample user interfaces of the map system in whicha shape-based geosearch is displayed, according to embodiments of thepresent disclosure. In FIG. 5E, the user has selected the shape button104, and a shape information window 514 is shown. In the user interfaceof FIG. 5E the user has drawn lines 518, however any shapes may be drawnon the map interface. Information related to the drawn lines 518 isdisplayed in the shape information window 514. For example, at 516 thestarting points, distance, and azimuth related to each line aredisplayed. Further, a total distance from the start to the end of theline is shown.

FIG. 5F shows a geosearch performed on the line shape drawn in FIG. 5E.Geosearch information window 520 indicates a search area 522, a timerange 524, and an object type 526 as described above with reference toFIG. 4B. The search area is indicated on the map interface by thehighlighted area 528 along the drawn line. The geosearch may beperformed, and results may be shown, in a manner similar to thatdescribed above with reference to FIGS. 4B-4D. For example, geosearchalong a path may be used to determine points of interest along thatpath.

FIG. 5G illustrates a sample user interface of the map system in which akeyword object search is displayed, according to an embodiment of thepresent disclosure. The user may type words, keywords, numbers, and/orgeographic coordinates, among others, into the search box 112. In FIG.5G, the user has typed Bank (530). As the user types, the map systemautomatically searches for objects and/or features that match theinformation typed. Matching may be performed based on object data and/ormetadata. Search results are displayed as shown at 532 in FIG. 5G. Inthe example, a list of banks (bank features) is shown. The user may thenselect from the list shown, at which point the map system automaticallyzooms to the selected feature and indicates the selected feature with anarrow 534. In various embodiments, the selected feature may be indicatedby highlighting, outlining, and/or any other type of indicator. In anembodiment, the search box 112 may be linked to a gazetteer so as toenable simple word searches for particular geographic locations. Forexample, a search for a city name, New York, may be linked with thegeographic coordinates of the city, taking the user directly to thatlocation on the map interface.

FIG. 5H illustrates an example of a UTF grid of the map system,according to an embodiment of the present disclosure. In an embodiment,the UTF grid enables feature outlining and/or highlighting of manyobjects with client-side components. In one embodiment, each map tile(or image) of the map interface includes an associated textual UTF (UCSTransformation Format) grid. In FIG. 5H, an example map tile 526 isshown next to an associated example UTF grid 538. In this example, themap tile and associated UTF grid are generated by the server-sidecomponents and sent to the client-side components. In the UTF grid, eachcharacter represents a pixel in the map tile image, and each characterindicates what feature is associated with the pixel. Each character inthe UTF grid may additionally be associated with a feature identifierwhich may be used to request metadata associated with that feature.

Contiguous regions of characters in the UTF grid indicate the bounds ofa particular feature, and may be used by the client-side components toprovide the feature highlighting and/or outlining. For example, when auser hovers a mouse pointer over a feature on a map tile, the map systemdetermines the character and portion of the UTF grid associated with thepixel hovered over, draws a feature outline based on the UTF grid, andmay additionally access metadata associated with the feature based onthe feature identifier associated with the feature. In an embodiment,the UTF grid is sent to the client-side components in a JSON (JavaScriptObject Notation) format.

FIG. 6A shows a flow diagram depicting illustrative client-sideoperations of the map system, according to an embodiment of the presentdisclosure. In various embodiments, fewer blocks or additional blocksmay be included in the process, or various blocks may be performed in anorder different from that shown in FIG. 6A. In an embodiment, one ormore blocks in FIG. 6A may be performed by client-side components of themap system, for example, computer system 800 (described below inreference to FIG. 8D).

At block 602, the map system provides a user interface (for example, theuser interface of FIG. 1) to the user. As described above and below, theuser interface may be provided to the user through any electronicdevice, such as a desktop computer, a laptop computer, a mobilesmartphone, and/or a tablet, among others. At block 604, an input isreceived from the user of the map system. For example, the user may usea mouse to roll over and/or click on an item of the user interface, orthe user may touch the display of the interface (in the example of atouch screen device).

Inputs received from the user may include, for example, hovering over,rolling over, and/or touching and object in the user interface (606);filling out a text field (614); drawing a shape in the user interface(608), and/or drawing a selection box and/or shape in the user interface(610); among other actions or inputs as described above.

At block 612, any of inputs 606, 614, 608, and 610 may cause the mapsystem to perform client-side actions to update the user interface. Forexample, hovering over an object (606) may result in the client-sidecomponents of the map system to access the UTF grid, determine theboundaries of the object, and draw an outline around the hovered-overobject. In another example, filling out a text field (614) may includethe user inputting data into the map system. In this example, the usermay input geographic coordinates, metadata, and/or other types of datato the map system. These actions may result in, for example, theclient-side components of the map system storing the inputted dataand/or taking an action based on the inputted data. For example, theuser inputting coordinates may result in the map interface being updatedto display the inputted information, such as an inputted name overlayinga particular object. In yet another example, the actions/inputs ofdrawing a shape (608) and/or drawing a selection (610) may result in theclient-side components of the map system to update the user interfacewith colored and/or highlighted shapes (see, for example, FIG. 3A).

In an embodiment, one or more blocks in FIG. 6A may be performed byserver-side components of the map system, for example, server 830(described below in reference to FIG. 8D).

FIG. 6B shows a flow diagram depicting illustrative client-side metadataretrieval of the map system, according to an embodiment of the presentdisclosure. In various embodiments, fewer blocks or additional blocksmay be included in the process, or various blocks may be performed in anorder different from that shown in FIG. 6B. In an embodiment, one ormore blocks in FIG. 6B may be performed by client-side components of themap system, for example, computer system 800.

At block 620, the client-side components of the map system detect thatthe user is hovering over and/or touching an object in the userinterface. At block 622, and as described above, the client-sidecomponents may access the UTF grid to determine the feature identifierand object boundaries associated with the hovered-over object. Then, atblock 624, the client-side components may render the feature shape onthe image or map interface. The feature shape may be rendered as anoutline and/or other highlighting.

At block 636, the client-side components detect whether the user hasselected the object. Objects may be selected, for example, if the userclicks on the object and or touches the object. If the user has selectedthe object, then at block 628, the client-side components query theserver-side components to retrieve metadata associated with the selectedobject. In an embodiment, querying of the server-side components mayinclude transmitting the feature identifier associated with the selectedobject to the server, the server retrieving from a database the relevantmetadata, and the server transmitting the retrieved metadata back to theclient-side components.

At block 630, the metadata is received by the client-side components anddisplayed to the user. For example, the metadata associated with theselected object may be displayed to the user in the user interface in adedicated metadata window, among other possibilities.

In an embodiment, one or more blocks in FIG. 6B may be performed byserver-side components of the map system, for example, server 830.

FIG. 7A shows a flow diagram depicting illustrative server-sideoperations of the map system, according to an embodiment of the presentdisclosure. In various embodiments, fewer blocks or additional blocksmay be included in the process, or various blocks may be performed in anorder different from that shown in FIG. 7A. In an embodiment, one ormore blocks in FIG. 7A may be performed by server-side components of themap system, for example, server 830.

Server-side operations of the map system may include composing andupdating the map tiles that make up the map interface. For example, whenthe user changes the selection of the base layer and/or one or more ofthe vector layers, the map tiles are re-composed and updated in the mapinterface to reflect the user's selection. Selection of objectsresulting in highlighting of those objects may also involvere-composition of the map tiles. Further, UTF grids may be generated bythe server-side components for each map tile composed.

At block 702, the user interface is provided to the user. At block 704an input from the user is received. Inputs received from the user thatmay result in server-side operations may include, for example, an objectselection (706), a change in layer selection (708), a geosearch (710),generating a heatmap (712), searching from the search box (714), and/orpanning or zooming the map interface, among others.

At block 716, the client-side components of the map system may query theserver-side components in response to any of inputs 706, 708, 710, 712,and 714 from the user. The server-side components then update andre-compose the map tiles and UTF grids of the map interface inaccordance with the user input (as described below in reference to FIG.7B), and transmits those updated map tiles and UTF grids back to theclient-side components.

At block 718, the client-side components receive the updated map tileinformation from the server, and at block 720 the user interface isupdated with the received information.

In an embodiment, additional information and/or data, in addition toupdated map tiles, may be transmitted to the client-side components fromthe server-side components. For example, object metadata may betransmitted in response to a user selecting an object.

In an embodiment, one or more blocks in FIG. 7A may be performed byclient-side components of the map system, for example, computer system800.

FIG. 7B shows a flow diagram depicting illustrative server-side layercomposition of the map system, according to an embodiment of the presentdisclosure. In various embodiments, fewer blocks or additional blocksmay be included in the process, or various blocks may be performed in anorder different from that shown in FIG. 7B. In an embodiment, one ormore blocks in FIG. 7B may be performed by server-side components of themap system, for example, server 830.

At block 730, a query is received by the server-side components from theclient-side components. Such a query may originate, for example, atblock 716 of FIG. 7A. At block 732, the server-side components determinethe map tile composition based on the query. For example, if the userhas selected an object or group of objects, the map tiles containingthose objects may be updated to include highlighted objects. In anotherexample, if the user has changed the layer selection, the map tiles maybe updated to include only those layers that are currently selected. Inthe example of FIG. 7B, the layers currently selected are determined,and the layers are composed and/or rendered into the map tiles. Inanother example, if the user has performed a geosearch and selected toadd the search result objects to the map interface, the map tiles areupdated to include those search result objects. In yet another example,when the user has generated a heatmap, the map tiles are updated to showthe generated heatmap. In another example, if the user searches via thesearch box, the selected objects may be highlighted in the re-composedmap tiles. In another example, when the user pans and/or zooms in themap interface, the map tiles are updated to reflect the new viewselected by the user. In all cases, and updated UTF grid may also begenerated for each composed map tile.

At block 734, the map system determines whether the layers necessary tocompose the requested map tiles are cached. For example, when a layer isselected by the user, that layer may be composed by the map system andplaced in a memory of the server-side components for future retrieval.Caching of composed layers may obviate the need for recomposing thoselayers later, which advantageously may save time and/or processingpower.

If the required layers are cached, then at block 740 the layers arecomposed into the requested map tiles and, at block 742, transmitted tothe client-side components.

When the required layers are not cached, at block 736, the server-sidecomponents calculate and/or compose the requested layer and or layers,and may then, at block 738, optionally cache the newly composed layersfor future retrieval. Then, at blocks 740 and 742, the layers arecomposed into map tiles and provided to the client-side components.

In an embodiment, entire map tiles may be cached by the server-sidecomponents. In an embodiment, the size and/or quality of the map tilesthat make up that map interface may be selected and/or dynamicallyselected based on at least one of: the bandwidth available fortransmitting the map tiles to the client-side components, the size ofthe map interface, and/or the complexity of the layer composition, amongother factors. In an embodiment, the map tiles comprise images, forexample, in one or more of the following formats: PNG, GIF, JPEG, TIFF,BMP, and/or any other type of appropriate image format.

In an embodiment, the layer and object data composed into layers and maptiles comprises vector data. The vector data (for example, object data)may include associated metadata, as described above. In an embodiment,the vector, layer, and/or object data and associated metadata mayoriginate from one or more databases and/or electronic data stores.

In an embodiment, one or more blocks in FIG. 7B may be performed byclient-side components of the map system, for example, computer system800.

In an embodiment, the map system may display more than 50 millionselectable features to a user simultaneously. In an embodiment, the mapsystem may support tens or hundreds of concurrent users accessing thesame map and object data. In an embodiment, map and object data used bythe map system may be mirrored and/or spread across multiple computers,servers, and/or server-side components.

In an embodiment, rather than updating the map tiles to reflect aselection by the user of one or more objects, the map system may show anapproximation of the selection to the user based on client-sideprocessing.

In an embodiment, a user may drag and drop files, for example, vectordata and/or vector layers, onto the user interface of the map system,causing the map system to automatically render the file in the mapinterface.

In an embodiment, icons and/or styles associated with various objects inthe map interface may be updated and/or changed by the user. Forexample, the styles of the various objects may be specified in or by astyle data file. The style data file may be formatted according to aparticular format or standard readable by the map system. In anembodiment, the style data file is formatted according to the JSONformat standard. The user may thus change the look of the objects andshapes rendered in the map interface of the map system by changing thestyle data file. The style data file may further define the looks forobject and terrain (among other items and data) at various zoom levels.

In an embodiment, objects, notes, metadata, and/or other types of datamay be added to the map system by the user through the user interface.In an embodiment, user added information may be shared between multipleusers of the map system. In an embodiment, a user of the map system mayadd annotations and shapes to the map interface that may be saved andshared with other users. In an embodiment, a user of the map system mayshare a selection of objects with one or more other users.

In an embodiment, the user interface of the map system may include atimeline window. The timeline window may enable the user to view objectsand layers specific to particular moments in time and/or time periods.In an embodiment, the user may view tolerance ellipses overlaid on themap interface indicating the likely position of an object across aparticular time period.

In an embodiment, the map system may include elevation profiling.Elevation profiling may allow a user of the system to determine theelevation along a path on the map interface, to perform a viewshedanalysis (determine objects and/or terrain viewable from a particularlocation), to perform a reverse-viewshed analysis (for a particularlocation, determine objects and/or terrain that may view the location),among others.

In an embodiment, vector data, object data, metadata, and/or other typesof data may be prepared before it is entered into or accessed by the mapsystem. For example, the data may be converted from one format toanother, may be crawled for common items of metadata, and/or may beprepared for application of a style file or style information, amongother action. In an embodiment, a layer ontology may be automaticallygenerated based on a group of data. In an embodiment, the map system mayaccess common data sources available on the Internet, for example, roaddata available from openstreetmap.org.

In an embodiment, roads shown in the map interface are labeled withtheir names, and buildings are rendered in faux-3D to indicate thebuilding heights. In an embodiment, Blue Force Tracking may beintegrated into the map system as a layer with the characteristics ofboth a static vector layer and a dynamic selection layer. A Blue Forcelayer may enable the use of the map system for live operationalanalysis. In an embodiment, the map system may quickly render detailedchloropleths or heatmaps with minimal data transfer. For example, thesystem may render a chloropleth with a property value on the individualshapes of the properties themselves, rather than aggregating thisinformation on a county or zip code level.

Advantageously, the map system displays many items of data, objects,features, and/or layers in a single map interface. A user may easilyinteract with things on the map and gather information by hovering overor selecting features, even though those features may not be labeled.The user may select features, may “drill down” on a particular type offeature (for example, roads), may view features through histograms, mayuse histograms to determine common characteristics (for example,determine the most common speed limit), and/or may determinecorrelations among features (for example, see that slower speed limitareas are centered around schools). Further, the map system may beuseful in many different situations. For example, the system may beuseful to operational planners and/or disaster relief personnel.

Additionally, the map system accomplishes at least three core ideas:providing a robust and fast back-end (server-side) renderer, keepingdata on the back-end, and only transferring the data necessary to haveinteractivity. In one embodiment, the primary function of theserver-side components is rendering map tiles. The server is capable ofdrawing very detailed maps with a variety of styles that can be based onvector metadata. Rendered map tiles for a vector layer are cached, andseveral of these layer tiles are drawn on top of one another to producethe final tile that is sent to the client-side browser. Map tilerendering is fast enough for displaying dynamic tiles for selection andhighlight to the user. Server-side operations allow for dynamicselections of very large numbers of features, calculation of thehistogram, determining the number of items shown and/or selected, anddrawing the selection, for example. Further, the heatmap may includelarge numbers of points without incurring the cost of transferring thosepoints to the client-side browser. Additionally, transferring only asmuch data as necessary to have interactivity enables quick serverrendering of dynamic selections and vector layers. On the other hand,highlighting hovered-over features may be performed client-side nearlyinstantaneously, and provides useful feedback that enhances theinteractivity of the map system. In an embodiment, to avoid transferringtoo much geometric data, the geometries of objects (in the map tiles andUTF grid) are down-sampled depending on how zoomed in the user is to themap interface. Thus, map tiles may be rendered and presented to a userof the map system in a dynamic and useable manner.

Object Centric Data Model

To provide a framework for the following discussion of specific systemsand methods described above and below, an example database system 1210using an ontology 1205 will now be described. This description isprovided for the purpose of providing an example and is not intended tolimit the techniques to the example data model, the example databasesystem, or the example database system's use of an ontology to representinformation.

In one embodiment, a body of data is conceptually structured accordingto an object-centric data model represented by ontology 1205. Theconceptual data model is independent of any particular database used fordurably storing one or more database(s) 1209 based on the ontology 1205.For example, each object of the conceptual data model may correspond toone or more rows in a relational database or an entry in LightweightDirectory Access Protocol (LDAP) database, or any combination of one ormore databases.

FIG. 8A illustrates an object-centric conceptual data model according toan embodiment. An ontology 1205, as noted above, may include storedinformation providing a data model for storage of data in the database1209. The ontology 1205 may be defined by one or more object types,which may each be associated with one or more property types. At thehighest level of abstraction, data object 1201 is a container forinformation representing things in the world. For example, data object1201 can represent an entity such as a person, a place, an organization,a market instrument, or other noun. Data object 1201 can represent anevent that happens at a point in time or for a duration. Data object1201 can represent a document or other unstructured data source such asan e-mail message, a news report, or a written paper or article. Eachdata object 1201 is associated with a unique identifier that uniquelyidentifies the data object within the database system.

Different types of data objects may have different property types. Forexample, a “Person” data object might have an “Eye Color” property typeand an “Event” data object might have a “Date” property type. Eachproperty 1203 as represented by data in the database system 1210 mayhave a property type defined by the ontology 1205 used by the database1205.

Objects may be instantiated in the database 1209 in accordance with thecorresponding object definition for the particular object in theontology 1205. For example, a specific monetary payment (e.g., an objectof type “event”) of US$30.00 (e.g., a property of type “currency”)taking place on 3/27/2009 (e.g., a property of type “date”) may bestored in the database 1209 as an event object with associated currencyand date properties as defined within the ontology 1205.

The data objects defined in the ontology 1205 may support propertymultiplicity. In particular, a data object 1201 may be allowed to havemore than one property 1203 of the same property type. For example, a“Person” data object might have multiple “Address” properties ormultiple “Name” properties.

Each link 1202 represents a connection between two data objects 1201. Inone embodiment, the connection is either through a relationship, anevent, or through matching properties. A relationship connection may beasymmetrical or symmetrical. For example, “Person” data object A may beconnected to “Person” data object B by a “Child Of” relationship (where“Person” data object B has an asymmetric “Parent Of” relationship to“Person” data object A), a “Kin Of” symmetric relationship to “Person”data object C, and an asymmetric “Member Of” relationship to“Organization” data object X. The type of relationship between two dataobjects may vary depending on the types of the data objects. Forexample, “Person” data object A may have an “Appears In” relationshipwith “Document” data object Y or have a “Participate In” relationshipwith “Event” data object E. As an example of an event connection, two“Person” data objects may be connected by an “Airline Flight” dataobject representing a particular airline flight if they traveledtogether on that flight, or by a “Meeting” data object representing aparticular meeting if they both attended that meeting. In oneembodiment, when two data objects are connected by an event, they arealso connected by relationships, in which each data object has aspecific relationship to the event, such as, for example, an “AppearsIn” relationship.

As an example of a matching properties connection, two “Person” dataobjects representing a brother and a sister, may both have an “Address”property that indicates where they live. If the brother and the sisterlive in the same home, then their “Address” properties likely containsimilar, if not identical property values. In one embodiment, a linkbetween two data objects may be established based on similar or matchingproperties (e.g., property types and/or property values) of the dataobjects. These are just some examples of the types of connections thatmay be represented by a link and other types of connections may berepresented; embodiments are not limited to any particular types ofconnections between data objects. For example, a document might containreferences to two different objects. For example, a document may containa reference to a payment (one object), and a person (a second object). Alink between these two objects may represent a connection between thesetwo entities through their co-occurrence within the same document.

Each data object 1201 can have multiple links with another data object1201 to form a link set 1204. For example, two “Person” data objectsrepresenting a husband and a wife could be linked through a “Spouse Of”relationship, a matching “Address” property, and one or more matching“Event” properties (e.g., a wedding). Each link 1202 as represented bydata in a database may have a link type defined by the database ontologyused by the database.

FIG. 8B is a block diagram illustrating exemplary components and datathat may be used in identifying and storing data according to anontology. In this example, the ontology may be configured, and data inthe data model populated, by a system of parsers and ontologyconfiguration tools. In the embodiment of FIG. 8B, input data 1300 isprovided to parser 1302. The input data may comprise data from one ormore sources. For example, an institution may have one or more databaseswith information on credit card transactions, rental cars, and people.The databases may contain a variety of related information andattributes about each type of data, such as a “date” for a credit cardtransaction, an address for a person, and a date for when a rental caris rented. The parser 1302 is able to read a variety of source inputdata types and determine which type of data it is reading.

In accordance with the discussion above, the example ontology 1205comprises stored information providing the data model of data stored indatabase 1209, and the ontology is defined by one or more object types1310, one or more property types 1316, and one or more link types 1330.Based on information determined by the parser 1302 or other mapping ofsource input information to object type, one or more data objects 1201may be instantiated in the database 209 based on respective determinedobject types 1310, and each of the objects 1201 has one or moreproperties 1203 that are instantiated based on property types 1316. Twodata objects 1201 may be connected by one or more links 1202 that may beinstantiated based on link types 1330. The property types 1316 each maycomprise one or more data types 1318, such as a string, number, etc.Property types 1316 may be instantiated based on a base property type1320. For example, a base property type 1320 may be “Locations” and aproperty type 1316 may be “Home.”

In an embodiment, a user of the system uses an object type editor 1324to create and/or modify the object types 1310 and define attributes ofthe object types. In an embodiment, a user of the system uses a propertytype editor 1326 to create and/or modify the property types 1316 anddefine attributes of the property types. In an embodiment, a user of thesystem uses link type editor 1328 to create the link types 1330.Alternatively, other programs, processes, or programmatic controls maybe used to create link types and property types and define attributes,and using editors is not required.

In an embodiment, creating a property type 1316 using the property typeeditor 1326 involves defining at least one parser definition using aparser editor 1322. A parser definition comprises metadata that informsparser 1302 how to parse input data 1300 to determine whether values inthe input data can be assigned to the property type 1316 that isassociated with the parser definition. In an embodiment, each parserdefinition may comprise a regular expression parser 1304A or a codemodule parser 1304B. In other embodiments, other kinds of parserdefinitions may be provided using scripts or other programmaticelements. Once defined, both a regular expression parser 1304A and acode module parser 1304B can provide input to parser 1302 to controlparsing of input data 1300.

Using the data types defined in the ontology, input data 1300 may beparsed by the parser 1302 determine which object type 1310 shouldreceive data from a record created from the input data, and whichproperty types 1316 should be assigned to data from individual fieldvalues in the input data. Based on the object-property mapping 1301, theparser 1302 selects one of the parser definitions that is associatedwith a property type in the input data. The parser parses an input datafield using the selected parser definition, resulting in creating new ormodified data 1303. The new or modified data 1303 is added to thedatabase 1209 according to ontology 205 by storing values of the new ormodified data in a property of the specified property type. As a result,input data 1300 having varying format or syntax can be created indatabase 1209. The ontology 1205 may be modified at any time usingobject type editor 1324, property type editor 1326, and link type editor1328, or under program control without human use of an editor. Parsereditor 1322 enables creating multiple parser definitions that cansuccessfully parse input data 1300 having varying format or syntax anddetermine which property types should be used to transform input data300 into new or modified input data 1303.

The properties, objects, and links (e.g. relationships) between theobjects can be visualized using a graphical user interface (GUI). Forexample, FIG. 8C displays a user interface showing a graphrepresentation 1403 of relationships (including relationships and/orlinks 1404, 1405, 1406, 1407, 1408, 1409, 1410, 1411, 1412, and 1413)between the data objects (including data objects 1421, 1422, 1423, 1424,1425, 1426, 1427, 1428, and 1429) that are represented as nodes in theexample of FIG. 8C. In this embodiment, the data objects include personobjects 1421, 1422, 1423, 1424, 1425, and 1426; a flight object 1427; afinancial account 1428; and a computer object 1429. In this example,each person node (associated with person data objects), flight node(associated with flight data objects), financial account node(associated with financial account data objects), and computer node(associated with computer data objects) may have relationships and/orlinks with any of the other nodes through, for example, other objectssuch as payment objects.

For example, in FIG. 8C, relationship 1404 is based on a paymentassociated with the individuals indicated in person data objects 1421and 1423. The link 1404 represents these shared payments (for example,the individual associated with data object 1421 may have paid theindividual associated with data object 1423 on three occasions). Therelationship is further indicated by the common relationship betweenperson data objects 1421 and 1423 and financial account data object1428. For example, link 1411 indicates that person data object 1421transferred money into financial account data object 1428, while persondata object 1423 transferred money out of financial account data object1428. In another example, the relationships between person data objects1424 and 1425 and flight data object 1427 are indicated by links 1406,1409, and 1410. In this example, person data objects 1424 and 1425 havea common address and were passengers on the same flight data object1427. In an embodiment, further details related to the relationshipsbetween the various objects may be displayed. For example, links 1411and 1412 may, in some embodiments, indicate the timing of the respectivemoney transfers. In another example, the time of the flight associatedwith the flight data object 1427 may be shown.

Relationships between data objects may be stored as links, or in someembodiments, as properties, where a relationship may be detected betweenthe properties. In some cases, as stated above, the links may bedirectional. For example, a payment link may have a direction associatedwith the payment, where one person object is a receiver of a payment,and another person object is the payer of payment.

In various embodiments, data objects may further include geographicalmetadata and/or links. Such geographical metadata may be accessed by theinteractive data object map system for displaying objects and featureson the map interface (as described above).

In addition to visually showing relationships between the data objects,the user interface may allow various other manipulations. For example,the objects within database 1108 may be searched using a searchinterface 1450 (e.g., text string matching of object properties),inspected (e.g., properties and associated data viewed), filtered (e.g.,narrowing the universe of objects into sets and subsets by properties orrelationships), and statistically aggregated (e.g., numericallysummarized based on summarization criteria), among other operations andvisualizations. Additionally, as described above, objects withindatabase 1108 may be searched, accessed, and implemented in the mapinterface of the interactive data object map system via, for example, ageosearch and/or radius search.

Implementation Mechanisms

According to an embodiment, the interactive data object map system andother methods and techniques described herein are implemented by one ormore special-purpose computing devices. The special-purpose computingdevices may be hard-wired to perform the techniques, or may includedigital electronic devices such as one or more application-specificintegrated circuits (ASICs) or field programmable gate arrays (FPGAs)that are persistently programmed to perform the techniques, or mayinclude one or more general purpose hardware processors programmed toperform the techniques pursuant to program instructions in firmware,memory, other storage, or a combination. Such special-purpose computingdevices may also combine custom hard-wired logic, ASICs, or FPGAs withcustom programming to accomplish the techniques. The special-purposecomputing devices may be desktop computer systems, server computersystems, portable computer systems, handheld devices, networking devicesor any other device or combination of devices that incorporatehard-wired and/or program logic to implement the techniques.

Computing device(s) are generally controlled and coordinated byoperating system software, such as iOS, Android, Chrome OS, Windows XP,Windows Vista, Windows 7, Windows 8, Windows Server, Windows CE, Unix,Linux, SunOS, Solaris, iOS, Blackberry OS, VxWorks, or other compatibleoperating systems. In other embodiments, the computing device may becontrolled by a proprietary operating system. Conventional operatingsystems control and schedule computer processes for execution, performmemory management, provide file system, networking, I/O services, andprovide a user interface functionality, such as a graphical userinterface (“GUI”), among other things.

For example, FIG. 8D is a block diagram that illustrates a computersystem 800 upon which the various systems and methods discussed hereinmay be implemented. Computer system 800 includes a bus 802 or othercommunication mechanism for communicating information, and a hardwareprocessor, or multiple processors, 804 coupled with bus 802 forprocessing information. Hardware processor(s) 804 may be, for example,one or more general purpose microprocessors.

Computer system 800 also includes a main memory 806, such as a randomaccess memory (RAM), cache and/or other dynamic storage devices, coupledto bus 802 for storing information and instructions to be executed byprocessor 804. Main memory 806 also may be used for storing temporaryvariables or other intermediate information during execution ofinstructions to be executed by processor 804. Such instructions, whenstored in storage media accessible to processor 804, render computersystem 800 into a special-purpose machine that is customized to performthe operations specified in the instructions.

Computer system 800 further includes a read only memory (ROM) 808 orother static storage device coupled to bus 802 for storing staticinformation and instructions for processor 804. A storage device 810,such as a magnetic disk, optical disk, or USB thumb drive (Flash drive),etc., is provided and coupled to bus 802 for storing information andinstructions.

Computer system 800 may be coupled via bus 802 to a display 812, such asa cathode ray tube (CRT), LCD display, or touch screen display, fordisplaying information to a computer user and/or receiving input fromthe user. An input device 814, including alphanumeric and other keys, iscoupled to bus 802 for communicating information and command selectionsto processor 804. Another type of user input device is cursor control816, such as a mouse, a trackball, or cursor direction keys forcommunicating direction information and command selections to processor804 and for controlling cursor movement on display 812. This inputdevice typically has two degrees of freedom in two axes, a first axis(e.g., x) and a second axis (e.g., y), that allows the device to specifypositions in a plane. In some embodiments, the same directioninformation and command selections as cursor control may be implementedvia receiving touches on a touch screen without a cursor.

Computing system 800 may include a user interface module, and/or variousother types of modules to implement a GUI, a map interface, and thevarious other aspects of the interactive data object map system. Themodules may be stored in a mass storage device as executable softwarecodes that are executed by the computing device(s). This and othermodules may include, by way of example, components, such as softwarecomponents, object-oriented software components, class components andtask components, processes, functions, attributes, procedures,subroutines, segments of program code, drivers, firmware, microcode,circuitry, data, databases, data structures, tables, arrays, andvariables.

In general, the word “module,” as used herein, refers to logic embodiedin hardware or firmware, or to a collection of software instructions,possibly having entry and exit points, written in a programminglanguage, such as, for example, Java, Lua, C or C++. A software modulemay be compiled and linked into an executable program, installed in adynamic link library, or may be written in an interpreted programminglanguage such as, for example, BASIC, Perl, or Python. It will beappreciated that software modules may be callable from other modules orfrom themselves, and/or may be invoked in response to detected events orinterrupts. Software modules configured for execution on computingdevices may be provided on a computer readable medium, such as a compactdisc, digital video disc, flash drive, magnetic disc, or any othertangible medium, or as a digital download (and may be originally storedin a compressed or installable format that requires installation,decompression or decryption prior to execution). Such software code maybe stored, partially or fully, on a memory device of the executingcomputing device, for execution by the computing device. Softwareinstructions may be embedded in firmware, such as an EPROM. It will befurther appreciated that hardware modules may be comprised of connectedlogic units, such as gates and flip-flops, and/or may be comprised ofprogrammable units, such as programmable gate arrays or processors. Themodules or computing device functionality described herein arepreferably implemented as software modules, but may be represented inhardware or firmware. Generally, the modules described herein refer tological modules that may be combined with other modules or divided intosub-modules despite their physical organization or storage.

Computer system 800 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 800 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 800 in response to processor(s) 804 executing one or moresequences of one or more modules and/or instructions contained in mainmemory 806. Such instructions may be read into main memory 806 fromanother storage medium, such as storage device 810. Execution of thesequences of instructions contained in main memory 806 causesprocessor(s) 804 to perform the process steps described herein. Inalternative embodiments, hard-wired circuitry may be used in place of orin combination with software instructions.

The term “non-transitory media,” and similar terms, as used hereinrefers to any media that store data and/or instructions that cause amachine to operate in a specific fashion. Such non-transitory media maycomprise non-volatile media and/or volatile media. Non-volatile mediaincludes, for example, optical or magnetic disks, such as storage device810. Volatile media includes dynamic memory, such as main memory 806.Common forms of non-transitory media include, for example, a floppydisk, a flexible disk, hard disk, solid state drive, magnetic tape, orany other magnetic data storage medium, a CD-ROM, any other optical datastorage medium, any physical medium with patterns of holes, a RAM, aPROM, and EPROM, a FLASH-EPROM, NVRAM, any other memory chip orcartridge, and networked versions of the same.

Non-transitory media is distinct from but may be used in conjunctionwith transmission media. Transmission media participates in transferringinformation between nontransitory media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 802. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 804 for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. The remote computer can load theinstructions and/or modules into its dynamic memory and send theinstructions over a telephone line using a modem. A modem local tocomputer system 800 can receive the data on the telephone line and usean infra-red transmitter to convert the data to an infra-red signal. Aninfra-red detector can receive the data carried in the infra-red signaland appropriate circuitry can place the data on bus 802. Bus 802 carriesthe data to main memory 806, from which processor 804 retrieves andexecutes the instructions. The instructions received by main memory 806may optionally be stored on storage device 810 either before or afterexecution by processor 804.

Computer system 800 also includes a communication interface 818 coupledto bus 802. Communication interface 818 provides a two-way datacommunication coupling to a network link 820 that is connected to alocal network 822. For example, communication interface 818 may be anintegrated services digital network (ISDN) card, cable modem, satellitemodem, or a modem to provide a data communication connection to acorresponding type of telephone line. As another example, communicationinterface 818 may be a local area network (LAN) card to provide a datacommunication connection to a compatible LAN (or WAN component tocommunicated with a WAN). Wireless links may also be implemented. In anysuch implementation, communication interface 818 sends and receiveselectrical, electromagnetic or optical signals that carry digital datastreams representing various types of information.

Network link 820 typically provides data communication through one ormore networks to other data devices. For example, network link 820 mayprovide a connection through local network 822 to a host computer 824 orto data equipment operated by an Internet Service Provider (ISP) 826.ISP 826 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the“Internet” 828. Local network 822 and Internet 828 both use electrical,electromagnetic or optical signals that carry digital data streams. Thesignals through the various networks and the signals on network link 820and through communication interface 818, which carry the digital data toand from computer system 800, are example forms of transmission media.

Computer system 800 can send messages and receive data, includingprogram code, through the network(s), network link 820 and communicationinterface 818. In the Internet example, a server 830 might transmit arequested code for an application program through Internet 828, ISP 826,local network 822 and communication interface 818. Server-sidecomponents of the interactive data object map system described above(for example, with reference to FIGS. 7A and 7B) may be implemented inthe server 830. For example, the server 830 may compose map layers andtiles, and transmit those map tiles to the computer system 800.

The computer system 800, on the other hand, may implement the theclient-side components of the map system as described above (forexample, with reference to FIGS. 6A and 6B). For example, the computersystem may receive map tiles and/or other code that may be executed byprocessor 804 as it is received, and/or stored in storage device 810, orother non-volatile storage for later execution. The computer system 800may further compose the map interface from the map tiles, display themap interface to the user, generate object outlines and otherfunctionality, and/or receive input from the user.

In an embodiment, the map system may be accessible by the user through aweb-based viewer, such as a web browser. In this embodiment, the mapinterface may be generated by the server 830 and/or the computer system800 and transmitted to the web browser of the user. The user may theninteract with the map interface through the web-browser. In anembodiment, the computer system 800 may comprise a mobile electronicdevice, such as a cell phone, smartphone, and/or tablet. The map systemmay be accessible by the user through such a mobile electronic device,among other types of electronic devices.

Each of the processes, methods, and algorithms described in thepreceding sections may be embodied in, and fully or partially automatedby, code modules executed by one or more computer systems or computerprocessors comprising computer hardware. The processes and algorithmsmay be implemented partially or wholly in application-specificcircuitry.

The various features and processes described above may be usedindependently of one another, or may be combined in various ways. Allpossible combinations and subcombinations are intended to fall withinthe scope of this disclosure. In addition, certain method or processblocks may be omitted in some implementations. The methods and processesdescribed herein are also not limited to any particular sequence, andthe blocks or states relating thereto can be performed in othersequences that are appropriate. For example, described blocks or statesmay be performed in an order other than that specifically disclosed, ormultiple blocks or states may be combined in a single block or state.The example blocks or states may be performed in serial, in parallel, orin some other manner. Blocks or states may be added to or removed fromthe disclosed example embodiments. The example systems and componentsdescribed herein may be configured differently than described. Forexample, elements may be added to, removed from, or rearranged comparedto the disclosed example embodiments.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached Figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure. The foregoing description details certainembodiments of the invention. It will be appreciated, however, that nomatter how detailed the foregoing appears in text, the invention can bepracticed in many ways. As is also stated above, it should be noted thatthe use of particular terminology when describing certain features oraspects of the invention should not be taken to imply that theterminology is being re-defined herein to be restricted to including anyspecific characteristics of the features or aspects of the inventionwith which that terminology is associated. The scope of the inventionshould therefore be construed in accordance with the appended claims andany equivalents thereof.

What is claimed is:
 1. A computer system comprising: a computer readablemedium storing software modules including computer executableinstructions; one or more hardware processors in communication with thecomputer readable medium, and configured to execute a user interfacemodule of the software modules in order to: display a plurality offeatures or objects each associated with metadata; detect a feature orobject in response to the user input of a particular feature or objectincluded on the interactive map; and in response to detecting thefeature or object hover input: determine a section of features orobjects associated with the particular feature or object; determineboundaries associated with the particular feature or object based on thedetermined section; and render an outline of the particular feature orobject on the interactive map based on the determined boundaries.
 2. Thecomputer system of claim 1, wherein the one or more hardware processorsare further configured to execute the computer-executable instructionsin order to: in response to the user hovering over the particularfeature or object, retrieve the metadata associated with the particularfeatures or objects and display the metadata to the user.
 3. Thecomputer system of claim 2, wherein retrieving the metadata associatedwith the particular feature is based at least in part on a featureidentifier associated with the feature or object.
 4. The computer systemof claim 1, wherein the one or more hardware processors are furtherconfigured to execute the computer-executable instructions in order to:in response to a first input from the user selecting a plurality of theincluded features or objects: determine metadata associated withrespective selected features or objects; and determine one or moremetadata categories associated with at least one of the determinedmetadata.
 5. The computer system of claim 4, wherein the one or morehardware processors are further configured to execute thecomputer-executable instructions in order, for each of the determinedmetadata categories, to: generate one or more histograms includingmetadata values or value ranges associated with respective selectedfeatures or objects, each of the histograms including a visual indicatorindicating a quantity of the respective selected plurality of featuresor objects included on the interactive map having the respectivemetadata value or value range; and display the one or more histograms onthe display along with the interactive map.
 6. The computer system ofclaim 5, wherein each of the histograms includes a visual indicatorindicating a quantity of the respective features of the plurality offeatures or objects included on the interactive map having therespective metadata value within the metadata category.
 7. The computersystem of claim 6, wherein each histogram of the one or more histogramsis specific to a particular metadata category.
 8. The computer system ofclaim 7, wherein each histogram of the one or more histograms comprisesa list of items of metadata specific to the particular metadata categoryof the histogram, wherein the list of items is organized in descendingorder from an item having the largest number of related features to anitem having the smallest number of related features.
 9. The computersystem of claim 6, wherein the one or more hardware processors areconfigured to execute the computer-executable instructions in order to:receive a user selection of a plurality of features or objectsassociated with the one or more histograms; and in response to the userselection: update the interactive map to display the plurality ofselected features or objects on the display; and highlight the pluralityof selected features or objects on the interactive map.
 10. The computersystem of claim 1, wherein the one or more hardware processors areconfigured to execute the computer-executable instructions in order to:associate the plurality of features with respective feature identifiers;and for each pixel of the interactive map, associate a character withthe pixel based on the represented feature or object.
 11. Acomputer-implemented method comprising: displaying a plurality offeatures or objects each associated with metadata; detecting a featureor object in response to the user input of a particular feature orobject included on the interactive map; and in response to detecting thefeature or object hover input: determining a section of features orobjects associated with the particular feature or object; determiningboundaries associated with the particular feature or object based on thedetermined section; and rendering an outline of the particular featureor object on the interactive map based on the determined boundaries. 12.The method of claim 10 further comprising: in response to the userhovering over the particular feature or object, retrieving the metadataassociated with the particular feature or object and displaying themetadata to the user.
 13. The method of claim 11, wherein retrieving themetadata associated with the particular feature or object is based atleast in part on a feature identifier associated with the feature orobject.
 14. The method of claim 12 further comprising: in response to afirst input from the user selecting a plurality of the includedfeatures: determining metadata associated with respective selectedfeatures or objects; and determining one or more metadata categoriesassociated with at least one of the determined metadata.
 15. The methodof claim 13 further comprising: for each of the determined metadatacategories: generating one or more histograms including metadata valuesor value ranges associated with respective selected features or objects,each of the histograms including a visual indicator indicating aquantity of the respective selected plurality of features or objectsincluded on the interactive map having the respective metadata value orvalue range; and displaying the one or more histograms on the displayalong with the interactive map.
 16. The method of claim 14, wherein eachhistogram of the one or more histograms comprises a list of items ofmetadata specific to the particular metadata category of the histogram,wherein the list of items is organized in descending order from an itemhaving the largest number of related features or objects to an itemhaving the smallest number of related objects.
 17. The method of claim14, further comprising: receiving a user selection of a plurality offeatures or objects associated with the one or more histograms; and inresponse to the user selection: updating the interactive map to displaythe plurality of selected features on the display; and highlighting theplurality of selected features or objects on the interactive map. 18.The method of claim 1, further comprising: associating the plurality offeatures with respective feature identifiers; and for each pixel of theinteractive map, associate a character with the pixel based on therepresented feature or object.